| Package | hl7.ehrs.ehrsfmr21 |
| Type | Requirements |
| Id | Id |
| FHIR Version | R5 |
| Source | http://hl7.org/ehrs/https://build.fhir.org/ig/mvdzel/ehrsfm-fhir-r5/Requirements-EHRSFMR2.1-CPS.3.2.html |
| Url | http://hl7.org/ehrs/Requirements/EHRSFMR2.1-CPS.3.2 |
| Version | 2.1.0 |
| Status | active |
| Date | 2024-11-26T16:30:50+00:00 |
| Name | CPS_3_2_Support_for_Patient_Context__Driven_Assessments |
| Title | CPS.3.2 Support for Patient Context- Driven Assessments (Function) |
| Experimental | False |
| Realm | uv |
| Authority | hl7 |
| Description | Offer prompts based on patient-specific data at the point of information capture for assessment purposes. |
| Purpose | When a clinician fills out an assessment, data entered is matched against data already in the system to identify potential linkages and optimize patient care. For example, the system could scan the medication list and the knowledge base to see if any of the symptoms are side effects of medication already prescribed. Important diagnoses could be brought to the doctor's attention, for instance ectopic pregnancy in a woman of child bearing age, or appendicitis in a geriatric patient who has abdominal pain. |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Offer prompts based on patient-specific data at the point of information capture for assessment purposes.
When a clinician fills out an assessment, data entered is matched against data already in the system to identify potential linkages and optimize patient care. For example, the system could scan the medication list and the knowledge base to see if any of the symptoms are side effects of medication already prescribed. Important diagnoses could be brought to the doctor's attention, for instance ectopic pregnancy in a woman of child bearing age, or appendicitis in a geriatric patient who has abdominal pain.
| CPS.3.2#01 | SHOULD |
The system SHOULD provide the ability to analyze assessment data entered during the encounter against health evidence based standards and best practices. |
| CPS.3.2#02 | MAY |
The system MAY analyze health data and patient context-driven assessments in terms of practice standards, and render notifications (e.g., of possible additional testing, possible diagnoses, or adjunctive treatment). |
| CPS.3.2#03 | SHOULD |
The system SHOULD provide the ability to analyze assessment data against data in the patient-specific problem list. |
| CPS.3.2#04 | SHOULD |
The system SHOULD provide the ability to manage care setting specific templates. |
| CPS.3.2#05 | MAY |
The system MAY provide the ability to render alerts based on patient-specific clinical data (e.g., age for neonates, pediatrics, geriatrics; conditions for impaired renal function; medication). |
| CPS.3.2#06 | SHOULD |
The system SHOULD provide the ability to maintain integrated, chief complaint -driven documentation templates. |
| CPS.3.2#07 | SHOULD |
The system SHOULD provide the ability to maintain integrated, diagnosis-driven documentation templates. |
| CPS.3.2#08 | SHOULD |
The system SHOULD provide the ability to maintain integrated, disposition-driven documentation templates. |
FHIR{
"resourceType" : "Requirements",
"id" : "EHRSFMR2.1-CPS.3.2",
"meta" : {
"profile" : [
"http://hl7.org/ehrs/StructureDefinition/FMFunction"
]
},
"text" : {
"status" : "extensions",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Offer prompts based on patient-specific data at the point of information capture for assessment purposes.</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>When a clinician fills out an assessment, data entered is matched against data already in the system to identify potential linkages and optimize patient care. For example, the system could scan the medication list and the knowledge base to see if any of the symptoms are side effects of medication already prescribed. Important diagnoses could be brought to the doctor's attention, for instance ectopic pregnancy in a woman of child bearing age, or appendicitis in a geriatric patient who has abdominal pain.</p>\n</div></span>\n \n\n \n\n \n <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.3.2#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to analyze assessment data entered during the encounter against health evidence based standards and best practices.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.3.2#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY analyze health data and patient context-driven assessments in terms of practice standards, and render notifications (e.g., of possible additional testing, possible diagnoses, or adjunctive treatment).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.3.2#03</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to analyze assessment data against data in the patient-specific problem list.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.3.2#04</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to manage care setting specific templates.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.3.2#05</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to render alerts based on patient-specific clinical data (e.g., age for neonates, pediatrics, geriatrics; conditions for impaired renal function; medication).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.3.2#06</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to maintain integrated, chief complaint -driven documentation templates.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.3.2#07</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to maintain integrated, diagnosis-driven documentation templates.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.3.2#08</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to maintain integrated, disposition-driven documentation templates.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"
},
"url" : "http://hl7.org/ehrs/Requirements/EHRSFMR2.1-CPS.3.2",
"version" : "2.1.0",
"name" : "CPS_3_2_Support_for_Patient_Context__Driven_Assessments",
"title" : "CPS.3.2 Support for Patient Context- Driven Assessments (Function)",
"status" : "active",
"date" : "2024-11-26T16:30:50+00:00",
"publisher" : "EHR WG",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/ehr"
}
]
}
],
"description" : "Offer prompts based on patient-specific data at the point of information capture for assessment purposes.",
"jurisdiction" : [
{
"coding" : [
{
"system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code" : "001",
"display" : "World"
}
]
}
],
"purpose" : "When a clinician fills out an assessment, data entered is matched against data already in the system to identify potential linkages and optimize patient care. For example, the system could scan the medication list and the knowledge base to see if any of the symptoms are side effects of medication already prescribed. Important diagnoses could be brought to the doctor's attention, for instance ectopic pregnancy in a woman of child bearing age, or appendicitis in a geriatric patient who has abdominal pain.",
"statement" : [
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CPS.3.2-01",
"label" : "CPS.3.2#01",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to analyze assessment data entered during the encounter against health evidence based standards and best practices.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.2.1.2#2"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CPS.3.2-02",
"label" : "CPS.3.2#02",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY analyze health data and patient context-driven assessments in terms of practice standards, and render notifications (e.g., of possible additional testing, possible diagnoses, or adjunctive treatment).",
"derivedFrom" : "EHR-S_FM_R1.1 DC.2.1.2#3"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CPS.3.2-03",
"label" : "CPS.3.2#03",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to analyze assessment data against data in the patient-specific problem list.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.2.1.2#4"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CPS.3.2-04",
"label" : "CPS.3.2#04",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to manage care setting specific templates."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CPS.3.2-05",
"label" : "CPS.3.2#05",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to render alerts based on patient-specific clinical data (e.g., age for neonates, pediatrics, geriatrics; conditions for impaired renal function; medication)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CPS.3.2-06",
"label" : "CPS.3.2#06",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to maintain integrated, chief complaint -driven documentation templates."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CPS.3.2-07",
"label" : "CPS.3.2#07",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to maintain integrated, diagnosis-driven documentation templates."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CPS.3.2-08",
"label" : "CPS.3.2#08",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to maintain integrated, disposition-driven documentation templates."
}
]
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.